-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[13_2] Unique upgrade workflow ID #41689
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41689/35558
|
A new Pull Request was created by @srimanob (Phat Srimanobhas) for master. It involves the following packages:
@bbilin, @cmsbuild, @AdrianoDee, @srimanob, @kskovpen, @sunilUIET can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test No change is expected from this PR as we currently do not have the workflow after 14800. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b9872a/32652/summary.html Comparison SummarySummary:
|
+pdmv |
+Upgrade |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This to make a unique upgrade workflow ID between CMSSW_12_4 and beyond after #41591
PR validation:
Running
runTheMatrix.py --what upgrade -n | grep 2023FS
, still get expected wf id.If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
There is a PR for 12_4, #41688. It has different defined
numWFConflict
to reflect the workflow in the release.Backport should be done to 13_1 (the same as this PR)